Automatic lidar calibration based on cross validation for autonomous driving

ABSTRACT

In one embodiment, a set of LIDAR images representing LIDAR point cloud data captured by a LIDAR device of an ADV at different points in time is received. For each of the LIDAR images, a perception method is utilized to determine a location of an obstacle captured in the LIDAR image in a local coordinate system. The LIDAR image is transformed using a coordinate converter (e.g., a LIDAR to GPS coordinate conversion logic or function) from the local coordinate system to a global coordinate system. The coordinate converter is optimized based on the transformed LIDAR images by adjusting one or more parameters of the coordinate converter and the above operations are iteratively performed to obtain a set of optimal parameters. The optimized coordinate converter can then be utilized to process subsequent LIDAR images during autonomous driving at real-time.

TECHNICAL FIELD

Embodiments of the present disclosure relate generally to operating autonomous vehicles. More particularly, embodiments of the disclosure relate to LIDAR calibration for autonomous driving.

BACKGROUND

Vehicles operating in an autonomous mode (e.g., driverless) can relieve occupants, especially the driver, from some driving-related responsibilities. When operating in an autonomous mode, the vehicle can navigate to various locations using onboard sensors, allowing the vehicle to travel with minimal human interaction or in some cases without any passengers.

A light detection and range (LIDAR) device is one of the most important and popular sensors of an autonomous driving vehicle (ADV). The accuracy and efficiency of autonomous driving heavily relies on the accuracy of the LIDAR device. Periodically, the LIDAR device requires calibration. LIDAR calibration is a challenging problem for a mass scale production that needs to be solved. There has been a lack of efficient way calibrating a LIDAR device.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the disclosure are illustrated by way of example and not limitation in the figures of the accompanying drawings in which like references indicate similar elements.

FIG. 1 is a block diagram illustrating a networked system according to one embodiment.

FIG. 2 is a block diagram illustrating an example of an autonomous vehicle according to one embodiment.

FIGS. 3A-3B are block diagrams illustrating an example of a perception and planning system used with an autonomous vehicle according to one embodiment.

FIG. 4 is a block diagram illustrating an example of a LIDAR calibration system according to one embodiment.

FIG. 5 is a diagram illustrating examples of LIDAR images for calibration purposes according to one embodiment.

FIG. 6 is a flow diagram illustrating an example of a LIDAR calibration process according to one embodiment.

FIG. 7 is a flow diagram illustrating an example of a LIDAR calibration process according to another embodiment.

FIG. 8 is a block diagram illustrating a data processing system according to one embodiment.

DETAILED DESCRIPTION

Various embodiments and aspects of the disclosures will be described with reference to details discussed below, and the accompanying drawings will illustrate the various embodiments. The following description and drawings are illustrative of the disclosure and are not to be construed as limiting the disclosure. Numerous specific details are described to provide a thorough understanding of various embodiments of the present disclosure. However, in certain instances, well-known or conventional details are not described in order to provide a concise discussion of embodiments of the present disclosures.

Reference in the specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in conjunction with the embodiment can be included in at least one embodiment of the disclosure. The appearances of the phrase “in one embodiment” in various places in the specification do not necessarily all refer to the same embodiment.

According to some embodiments, an ADV is driven around to collect LIDAR data such as LIDAR row point cloud data from a LIDAR device mounted on the ADV, corresponding location data (e.g., GPS data), and vehicle heading directions. The LIDAR data is obtained in a LIDAR space or LIDAR coordinate system. The LIDAR data may be converted in a vehicle coordinate system (e.g., center point of the rear axle of the vehicle, a local coordinate system relative to the vehicle). For each LIDAR image construed by the LIDAR data, a perception process or algorithm is utilized to identify and recognize an obstacle or object captured by the LIDAR image. The location of the obstacle is calculated in the LIDAR or vehicle coordinate space.

A coordinate converter is utilized to translate or convert the LIDAR image from the LIDAR coordinate space to a global coordinate system such as a GPS coordinate system. For a given set of parameters or coefficients of the coordinate converter, the translated LIDAR images are compared to each other to determine the consistency of the same obstacle captured by the LIDAR images. The parameters of the coordinate converter are adjusted and the above process is repeatedly performed to determine a set of optimal parameters of the coordinate converter, such that the consistency of the obstacle captured by the LIDAR images reach maximum, at which point, the coordinate converter is considered as an optimal coordinate converter. The optimal coordinate converter can then be uploaded onto an ADV to be utilized at real-time for processing LIDAR images. The coordinate converter can be represented by a quaternion function, also referred to as a Q function.

According to one embodiment, a set of LIDAR images representing LIDAR point cloud data captured by a LIDAR device of an ADV at different points in time is received. For each of the LIDAR images, a perception method is utilized to determine a location of an obstacle captured in the LIDAR image in a local coordinate system. The LIDAR image is transformed using a coordinate converter (e.g., a LIDAR to GPS coordinate conversion logic or function) from the local coordinate system to a global coordinate system. The coordinate converter is optimized based on the transformed LIDAR images by adjusting one or more parameters of the coordinate converter and the above operations are iteratively performed to obtain a set of optimal parameters. The optimized coordinate converter can then be utilized to process subsequent LIDAR images during autonomous driving at real-time.

In one embodiment, the transformed LIDAR images are examined to determine a consistency of the obstacle appearing in the transformed LIDAR images. The coordinate converter is repeatedly optimized until the consistency reaches above a predetermined threshold. Alternatively, the optimization is performed until a number of iterations reaches a predetermined threshold, upon which a set of parameters of the coordinate converter having the highest consistency is selected as an optimal set of parameter of the coordinate converter.

In one embodiment, in determining the consistency of the obstacle appearing in LIDAR images, a number of LIDAR images having an obstacle occurring therein are counted. When the coordinate converter produces the highest number of transformed LIDAR images having an obstacle captured therein, the coordinate converter is considered as an optimal coordinate converter and its associated set of parameters or coefficients is considered as an optimal set of parameters or coefficients. In one embodiment, the coordinate converter includes or is represented by a quaternion function, where the coefficients of the quaternion function are optimized using the techniques set forth above. In one embodiment, the iterative optimization is performed using a gradient decent method.

FIG. 1 is a block diagram illustrating an autonomous vehicle network configuration according to one embodiment of the disclosure. Referring to FIG. 1, network configuration 100 includes autonomous vehicle 101 that may be communicatively coupled to one or more servers 103-104 over a network 102. Although there is one autonomous vehicle shown, multiple autonomous vehicles can be coupled to each other and/or coupled to servers 103-104 over network 102. Network 102 may be any type of networks such as a local area network (LAN), a wide area network (WAN) such as the Internet, a cellular network, a satellite network, or a combination thereof, wired or wireless. Server(s) 103-104 may be any kind of servers or a cluster of servers, such as Web or cloud servers, application servers, backend servers, or a combination thereof. Servers 103-104 may be data analytics servers, content servers, traffic information servers, map and point of interest (MPOI) severs, or location servers, etc.

An autonomous vehicle refers to a vehicle that can be configured to in an autonomous mode in which the vehicle navigates through an environment with little or no input from a driver. Such an autonomous vehicle can include a sensor system having one or more sensors that are configured to detect information about the environment in which the vehicle operates. The vehicle and its associated controller(s) use the detected information to navigate through the environment. Autonomous vehicle 101 can operate in a manual mode, a full autonomous mode, or a partial autonomous mode.

In one embodiment, autonomous vehicle 101 includes, but is not limited to, perception and planning system 110, vehicle control system 111, wireless communication system 112, user interface system 113, infotainment system 114, and sensor system 115. Autonomous vehicle 101 may further include certain common components included in ordinary vehicles, such as, an engine, wheels, steering wheel, transmission, etc., which may be controlled by vehicle control system 111 and/or perception and planning system 110 using a variety of communication signals and/or commands, such as, for example, acceleration signals or commands, deceleration signals or commands, steering signals or commands, braking signals or commands, etc.

Components 110-115 may be communicatively coupled to each other via an interconnect, a bus, a network, or a combination thereof. For example, components 110-115 may be communicatively coupled to each other via a controller area network (CAN) bus. A CAN bus is a vehicle bus standard designed to allow microcontrollers and devices to communicate with each other in applications without a host computer. It is a message-based protocol, designed originally for multiplex electrical wiring within automobiles, but is also used in many other contexts.

Referring now to FIG. 2, in one embodiment, sensor system 115 includes, but it is not limited to, one or more cameras 211, global positioning system (GPS) unit 212, inertial measurement unit (IMU) 213, radar unit 214, and a light detection and range (LIDAR) unit 215. GPS system 212 may include a transceiver operable to provide information regarding the position of the autonomous vehicle. IMU unit 213 may sense position and orientation changes of the autonomous vehicle based on inertial acceleration. Radar unit 214 may represent a system that utilizes radio signals to sense objects within the local environment of the autonomous vehicle. In some embodiments, in addition to sensing objects, radar unit 214 may additionally sense the speed and/or heading of the objects. LIDAR unit 215 may sense objects in the environment in which the autonomous vehicle is located using lasers. LIDAR unit 215 could include one or more laser sources, a laser scanner, and one or more detectors, among other system components. Cameras 211 may include one or more devices to capture images of the environment surrounding the autonomous vehicle. Cameras 211 may be still cameras and/or video cameras. A camera may be mechanically movable, for example, by mounting the camera on a rotating and/or tilting a platform.

Sensor system 115 may further include other sensors, such as, a sonar sensor, an infrared sensor, a steering sensor, a throttle sensor, a braking sensor, and an audio sensor (e.g., microphone). An audio sensor may be configured to capture sound from the environment surrounding the autonomous vehicle. A steering sensor may be configured to sense the steering angle of a steering wheel, wheels of the vehicle, or a combination thereof. A throttle sensor and a braking sensor sense the throttle position and braking position of the vehicle, respectively. In some situations, a throttle sensor and a braking sensor may be integrated as an integrated throttle/braking sensor.

In one embodiment, vehicle control system 111 includes, but is not limited to, steering unit 201, throttle unit 202 (also referred to as an acceleration unit), and braking unit 203. Steering unit 201 is to adjust the direction or heading of the vehicle. Throttle unit 202 is to control the speed of the motor or engine that in turn controls the speed and acceleration of the vehicle. Braking unit 203 is to decelerate the vehicle by providing friction to slow the wheels or tires of the vehicle. Note that the components as shown in FIG. 2 may be implemented in hardware, software, or a combination thereof.

Referring back to FIG. 1, wireless communication system 112 is to allow communication between autonomous vehicle 101 and external systems, such as devices, sensors, other vehicles, etc. For example, wireless communication system 112 can wirelessly communicate with one or more devices directly or via a communication network, such as servers 103-104 over network 102. Wireless communication system 112 can use any cellular communication network or a wireless local area network (WLAN), e.g., using WiFi to communicate with another component or system. Wireless communication system 112 could communicate directly with a device (e.g., a mobile device of a passenger, a display device, a speaker within vehicle 101), for example, using an infrared link, Bluetooth, etc. User interface system 113 may be part of peripheral devices implemented within vehicle 101 including, for example, a keyboard, a touch screen display device, a microphone, and a speaker, etc.

Some or all of the functions of autonomous vehicle 101 may be controlled or managed by perception and planning system 110, especially when operating in an autonomous driving mode. Perception and planning system 110 includes the necessary hardware (e.g., processor(s), memory, storage) and software (e.g., operating system, planning and routing programs) to receive information from sensor system 115, control system 111, wireless communication system 112, and/or user interface system 113, process the received information, plan a route or path from a starting point to a destination point, and then drive vehicle 101 based on the planning and control information. Alternatively, perception and planning system 110 may be integrated with vehicle control system 111.

For example, a user as a passenger may specify a starting location and a destination of a trip, for example, via a user interface. Perception and planning system 110 obtains the trip related data. For example, perception and planning system 110 may obtain location and route information from an MPOI server, which may be a part of servers 103-104. The location server provides location services and the MPOI server provides map services and the POIs of certain locations. Alternatively, such location and MPOI information may be cached locally in a persistent storage device of perception and planning system 110.

While autonomous vehicle 101 is moving along the route, perception and planning system 110 may also obtain real-time traffic information from a traffic information system or server (TIS). Note that servers 103-104 may be operated by a third party entity. Alternatively, the functionalities of servers 103-104 may be integrated with perception and planning system 110. Based on the real-time traffic information, MPOI information, and location information, as well as real-time local environment data detected or sensed by sensor system 115 (e.g., obstacles, objects, nearby vehicles), perception and planning system 110 can plan an optimal route and drive vehicle 101, for example, via control system 111, according to the planned route to reach the specified destination safely and efficiently.

Server 103 may be a data analytics system to perform data analytics services for a variety of clients. In one embodiment, data analytics system 103 includes data collector 121 and machine learning engine 122. Data collector 121 collects driving statistics 123 from a variety of vehicles, either autonomous vehicles or regular vehicles driven by human drivers. Driving statistics 123 include information indicating the driving commands (e.g., throttle, brake, steering commands) issued and responses of the vehicles (e.g., speeds, accelerations, decelerations, directions) captured by sensors of the vehicles at different points in time. Driving statistics 123 may further include information describing the driving environments at different points in time, such as, for example, routes (including starting and destination locations), MPOIs, road conditions, weather conditions, etc.

Based on driving statistics 123, machine learning engine 122 generates or trains a set of rules, algorithms, and/or predictive models 124 for a variety of purposes. In one embodiment, algorithms 124 may include an algorithm for calibrating or optimizing a coordinate converter the converts a local coordinate system of the LIDAR images to a global coordinate system such as a GPS system, so that the LIDAR images can be utilized for autonomous driving. Algorithms 124 can then be uploaded on ADVs to be utilized during autonomous driving in real-time.

According to one embodiment, LIDAR calibration system 125 is configured to calibrate or optimize a coordinate converter using a set of LIDAR images collected over a period of time by a variety of ADVs, which may be collected by data collector 121. A coordinate converter configured with a set of parameters is utilized to translate or convert the LIDAR images from a local/relative coordinate space to a global/absolute coordinate system such as a GPS coordinate system. For a given set of parameters or coefficients of the coordinate converter, the translated LIDAR images are compared to each other to determine the consistency of the same obstacle captured by the LIDAR images. The parameters of the coordinate converter are adjusted and the above process is repeatedly performed to determine a set of optimal parameters of the coordinate converter, such that the consistency of the obstacle captured by the LIDAR images reach maximum, at which point, the coordinate converter is considered as an optimal coordinate converter. The optimal coordinate converter can then be uploaded onto an ADV to be utilized at real-time for processing LIDAR images. The coordinate converter can be represented by a quaternion function.

FIGS. 3A and 3B are block diagrams illustrating an example of a perception and planning system used with an autonomous vehicle according to one embodiment. System 300 may be implemented as a part of autonomous vehicle 101 of FIG. 1 including, but is not limited to, perception and planning system 110, control system 111, and sensor system 115. Referring to FIGS. 3A-3B, perception and planning system 110 includes, but is not limited to, localization module 301, perception module 302, prediction module 303, decision module 304, planning module 305, control module 306, routing module 307, and coordinate converter 308.

Some or all of modules 301-308 may be implemented in software, hardware, or a combination thereof. For example, these modules may be installed in persistent storage device 352, loaded into memory 351, and executed by one or more processors (not shown). Note that some or all of these modules may be communicatively coupled to or integrated with some or all modules of vehicle control system 111 of FIG. 2. Some of modules 301-308 may be integrated together as an integrated module.

Localization module 301 determines a current location of autonomous vehicle 300 (e.g., leveraging GPS unit 212) and manages any data related to a trip or route of a user. Localization module 301 (also referred to as a map and route module) manages any data related to a trip or route of a user. A user may log in and specify a starting location and a destination of a trip, for example, via a user interface. Localization module 301 communicates with other components of autonomous vehicle 300, such as map and route information 311, to obtain the trip related data. For example, localization module 301 may obtain location and route information from a location server and a map and POI (MPOI) server. A location server provides location services and an MPOI server provides map services and the POIs of certain locations, which may be cached as part of map and route information 311. While autonomous vehicle 300 is moving along the route, localization module 301 may also obtain real-time traffic information from a traffic information system or server.

Based on the sensor data provided by sensor system 115 and localization information obtained by localization module 301, a perception of the surrounding environment is determined by perception module 302. The perception information may represent what an ordinary driver would perceive surrounding a vehicle in which the driver is driving. The perception can include the lane configuration, traffic light signals, a relative position of another vehicle, a pedestrian, a building, crosswalk, or other traffic related signs (e.g., stop signs, yield signs), etc., for example, in a form of an object. The lane configuration includes information describing a lane or lanes, such as, for example, a shape of the lane (e.g., straight or curvature), a width of the lane, how many lanes in a road, one-way or two-way lane, merging or splitting lanes, exiting lane, etc.

Perception module 302 may include a computer vision system or functionalities of a computer vision system to process and analyze images captured by one or more cameras in order to identify objects and/or features in the environment of autonomous vehicle. The objects can include traffic signals, road way boundaries, other vehicles, pedestrians, and/or obstacles, etc. The computer vision system may use an object recognition algorithm, video tracking, and other computer vision techniques. In some embodiments, the computer vision system can map an environment, track objects, and estimate the speed of objects, etc. Perception module 302 can also detect objects based on other sensors data provided by other sensors such as a radar and/or LIDAR.

For each of the objects, prediction module 303 predicts what the object will behave under the circumstances. The prediction is performed based on the perception data perceiving the driving environment at the point in time in view of a set of map/rout information 311 and traffic rules 312. For example, if the object is a vehicle at an opposing direction and the current driving environment includes an intersection, prediction module 303 will predict whether the vehicle will likely move straight forward or make a turn. If the perception data indicates that the intersection has no traffic light, prediction module 303 may predict that the vehicle may have to fully stop prior to enter the intersection. If the perception data indicates that the vehicle is currently at a left-turn only lane or a right-turn only lane, prediction module 303 may predict that the vehicle will more likely make a left turn or right turn respectively.

For each of the objects, decision module 304 makes a decision regarding how to handle the object. For example, for a particular object (e.g., another vehicle in a crossing route) as well as its metadata describing the object (e.g., a speed, direction, turning angle), decision module 304 decides how to encounter the object (e.g., overtake, yield, stop, pass). Decision module 304 may make such decisions according to a set of rules such as traffic rules or driving rules 312, which may be stored in persistent storage device 352.

Routing module 307 is configured to provide one or more routes or paths from a starting point to a destination point. For a given trip from a start location to a destination location, for example, received from a user, routing module 307 obtains route and map information 311 and determines all possible routes or paths from the starting location to reach the destination location. Routing module 307 may generate a reference line in a form of a topographic map for each of the routes it determines from the starting location to reach the destination location. A reference line refers to an ideal route or path without any interference from others such as other vehicles, obstacles, or traffic condition. That is, if there is no other vehicle, pedestrians, or obstacles on the road, an ADV should exactly or closely follows the reference line. The topographic maps are then provided to decision module 304 and/or planning module 305. Decision module 304 and/or planning module 305 examine all of the possible routes to select and modify one of the most optimal routes in view of other data provided by other modules such as traffic conditions from localization module 301, driving environment perceived by perception module 302, and traffic condition predicted by prediction module 303. The actual path or route for controlling the ADV may be close to or different from the reference line provided by routing module 307 dependent upon the specific driving environment at the point in time.

Based on a decision for each of the objects perceived, planning module 305 plans a path or route for the autonomous vehicle, as well as driving parameters (e.g., distance, speed, and/or turning angle), using a reference line provided by routing module 307 as a basis. That is, for a given object, decision module 304 decides what to do with the object, while planning module 305 determines how to do it. For example, for a given object, decision module 304 may decide to pass the object, while planning module 305 may determine whether to pass on the left side or right side of the object. Planning and control data is generated by planning module 305 including information describing how vehicle 300 would move in a next moving cycle (e.g., next route/path segment). For example, the planning and control data may instruct vehicle 300 to move 10 meters at a speed of 30 mile per hour (mph), then change to a right lane at the speed of 25 mph.

Based on the planning and control data, control module 306 controls and drives the autonomous vehicle, by sending proper commands or signals to vehicle control system 111, according to a route or path defined by the planning and control data. The planning and control data include sufficient information to drive the vehicle from a first point to a second point of a route or path using appropriate vehicle settings or driving parameters (e.g., throttle, braking, steering commands) at different points in time along the path or route.

In one embodiment, the planning phase is performed in a number of planning cycles, also referred to as driving cycles, such as, for example, in every time interval of 100 milliseconds (ms). For each of the planning cycles or driving cycles, one or more control commands will be issued based on the planning and control data. That is, for every 100 ms, planning module 305 plans a next route segment or path segment, for example, including a target position and the time required for the ADV to reach the target position. Alternatively, planning module 305 may further specify the specific speed, direction, and/or steering angle, etc. In one embodiment, planning module 305 plans a route segment or path segment for the next predetermined period of time such as 5 seconds. For each planning cycle, planning module 305 plans a target position for the current cycle (e.g., next 5 seconds) based on a target position planned in a previous cycle. Control module 306 then generates one or more control commands (e.g., throttle, brake, steering control commands) based on the planning and control data of the current cycle.

Note that decision module 304 and planning module 305 may be integrated as an integrated module. Decision module 304/planning module 305 may include a navigation system or functionalities of a navigation system to determine a driving path for the autonomous vehicle. For example, the navigation system may determine a series of speeds and directional headings to affect movement of the autonomous vehicle along a path that substantially avoids perceived obstacles while generally advancing the autonomous vehicle along a roadway-based path leading to an ultimate destination. The destination may be set according to user inputs via user interface system 113. The navigation system may update the driving path dynamically while the autonomous vehicle is in operation. The navigation system can incorporate data from a GPS system and one or more maps so as to determine the driving path for the autonomous vehicle.

According to one embodiment, coordinate converter 308 is configured to convert or transform a LIDAR image captured by a LIDAR device from a local coordinate system (e.g., a relative coordinate system such as a LIDAR coordinate system) to a global coordinate system (e.g., an absolute coordinate system such as a GPS coordinate system) before the LIDAR image can be utilized for autonomous driving such as determining an absolute location of the obstacle and planning a path to navigating around the obstacle, etc. Coordinate converter 308 may be implemented as a part of perception module 302. When a LIDAR image capturing an obstacle, the coordinates or location of the obstacle is a relative location with respect to the mounting position of the LIDAR device. Such coordinates cannot be utilized for autonomous driving. They have to be converted to global or absolute coordinates such as GPS coordinates.

In one embodiment coordinate converter 308 is trained, calibrated, and optimized by a LIDAR calibration system such as LIDAR calibration system 125 based on a large amount of LIDAR images captured by the LIDAR device and repeatedly adjusting the parameters of the coordinate converter 308 until it operates in the most optimal way. The optimization may be performed offline or alternatively, the LIDAR images can be collected during the autonomous driving and stored as a part of driving statistics 313. A LIDAR calibration module 309 may be implemented to dynamically and periodically calibrate coordinate converter 308.

In one embodiment, coordinate converter 308 may be implemented or represented by a quaternion function, also referred to as a Q function. In mathematics, the quaternions are a number system that extends the complex numbers. And they are applied to mechanics in a three-dimensional (3D) space. A feature of quaternions is that multiplication of two quaternions is noncommutative. A quaternion is defined as the quotient of two directed lines in a 3D space or equivalently as the quotient of two vectors. Quaternions are generally represented in the following form: a+b*i+c*j+d*k, where a, b, c, and d are real numbers, and i, j, and k are the fundamental quaternion units. Quaternions find uses in both pure and applied mathematics, in particular for calculations involving three-dimensional rotations such as in 3D computer graphics, computer vision, and crystallographic texture analysis. For example, in determining a location of an object in the autonomous driving space, i may represent a front/back vector (e.g., heading direction); j may represent a left/right vector (e.g., roll angle); and k may represent an up/down vector (e.g., pitch angle) of a particular location.

FIG. 4 is a block diagram illustrating a LIDAR calibration system according to one embodiment. LIDAR calibration module 400 may be implemented as a part of LIDAR calibration system 125 of FIG. 1 or LIDAR calibration module 309 of FIG. 3A. Referring to FIG. 4, in one embodiment, LIDAR calibration module 400 includes a data collector 401, a perception module 402, coordinate converter or function 403, parameter optimizer 404, and obstacle overlap counter 405. Note that some or all of these modules 401-405 may be integrated into fewer modules. Data collector may be implemented as a part of data collector 121 of FIG. 1. Perception module 402 may be implemented as a part of perception module 302. Data collector 401 is configured to receive LIDAR images captured by a LIDAR device of an ADV when the ADV drove around a predetermined driving environment, where the driving environment includes a static obstacle therein that can be captured by the LIDAR device. The LIAR images may be stored in a persistent storage device as a part of LIDAR images 411. At least some or all of the LIDAR images would have captured the obstacle therein at different points in time of a time period (e.g., five seconds).

As described above, the operations of an ADV are performed in a form of cycles such as planning cycles. Each cycle will last approximately 100 ms. During the LIDAR scanning, the LIDAR data is continuously collected for 100 ms. In one embodiment, the 100 ms of LIDAR data are then utilized to form a LIDAR image. Thus, there will be a LIDAR image formed for every 100 ms. Typically, a LIDAR can spin 5-20 cycles per second. For the purpose of calibrating a coordinate converter, 5 minutes of LIDAR data, i.e., 5*60*10=3000 LIDAR images, may be utilized.

In one embodiment, for each of the LIDAR images, perception module 402 may perform a perception process on the LIDAR image to identify and recognize an obstacle captured by the LIDAR image. A position of the obstacle with respect to the position of the LIDAR device is determined. Such a position of the obstacle is referred to as a relative position in a local coordinate system (e.g., LIDAR coordinate space). A coordinate converter 403 with a given set of parameters is invoked to transform or translate the position of the obstacle from a local/relative coordinate space to a global/absolute coordinate space using GPS data associated with the LIDAR image. Once all of the LIDAR images have been transformed using the coordinate converter, the consistency of the obstacles captured by the transformed LIDAR images is measured. The consistency and its associated parameters of the coordinate converter are then stored as a part of coordinate conversion parameters 412. The above operations are iteratively performed by adjusting at least one parameter of the coordinate converter 403. With different set of parameters, the consistency of the obstacles captured by the LIDAR images may be different after the coordinate transformation.

According to one embodiment, one way to measure the consistency of the obstacle represented by the LIDAR images is to determine the overlap in position of the obstacles captured by the LIDAR images after the coordinate conversion. Obstacle overlap counter 405 is utilized to count a number of LIDAR images that captures an obstacle whose position overlaps with an obstacle of another LIDAR image.

Referring now to FIG. 5, in this example, LIDAR images 501-504 are captured and formed based on LIDAR data collected over a period of time. As described above, if a LIDAR image is formed for every 100 ms, LIDAR images 501-504 may represent 3000 LIDAR images over a time period of five minutes. At least some of the LIDAR images include an obstacle captured therein such as obstacles 511-514. In a percept situation, each of the LIDAR image should have captured the obstacle at the same or similar position, particularly within a short period of time or the obstacle is a static obstacle (non-moving obstacle).

After the coordinate conversions with a coordinate converter configured with a given set of parameters, some positions of the obstacles 511-514 may shift due to different parameter settings of the coordinate converter. By comparing and measuring the overlap of the obstacles 511-514 amongst the LIDAR images, a set of parameters can be determined for the most optimal coordinate converter. The rationale behind this approach is that if the coordinate converter is optimal, the positions of the obstacles 511-514 of the LIDAR images 501-504 should be consistent, i.e., the positions should be the same or close to the same. A set of parameters of the coordinate converter that produces the highest number of LIDAR images having overlapped obstacles would be considered as a set of optimal parameters.

In one embodiment, the optimization of the coordinate converter is iteratively performed with a different set of parameters in each iteration, until the consistency of the obstacle represented by the LIDAR images (e.g., a number of LIDAR images having an overlapped obstacle with another LIDAR image) is above a predetermined threshold. Alternatively, the optimization is iteratively performed until the number of iterations reaches a predetermined threshold, upon which the set of parameters that produce the highest consistency amongst all will be selected as the optimal set of parameters.

FIG. 6 is a flow diagram illustrating a process of LIDAR calibration according to one embodiment. Process 600 may be performed by processing logic which may include software, hardware, or a combination thereof. For example, process 600 may be performed by LIDAR calibration module 400. Referring to FIG. 6, in operation 601, processing logic receives a set of LIDAR images captured by a LIDAR device of an ADV, when the ADV was driving within a predetermined driving environment. In operation 602, for each of the LIDAR images, a perception method is utilized to determine a location of an obstacle captured in the LIDAR image in a local coordinate system (e.g., LIDAR relative coordinate space). In operation 603, a coordinate converter configured with a set of parameters is utilized to transform or convert the LIDAR image from the local coordinate system to a global coordinate system (e.g., GPS absolute coordinate space). In operation 604, the coordinate converter is optimized based on the location of the obstacle appearing in the transformed LIDAR images by adjusting at least one of the parameters of the coordinate converter. The optimized coordinate converter can then be uploaded to an ADV for processing LIDAR data at real-time.

FIG. 7 is a flow diagram illustrating a process of LIDAR calibration according to another embodiment. Process 700 may be performed by processing logic which may include software, hardware, or a combination thereof. For example, process 700 may be performed by LIDAR calibration module 400. Referring to FIG. 7, in operation 701, a coordinate converter is utilized to transform LIDAR images from a local coordinate system to a global coordinate system. In operation 702, processing logic determines a number of the transformed LIDAR images that have an obstacle whose position overlaps with an obstacle of another transformed LIDAR image. In operation 703, processing logic determines whether the number of LIDAR images with overlapped obstacle is greater than a predetermined threshold. If so, in operation 706, the set of parameters of the coordinate converter is considered as a set of optimal parameters. If the number of LIDAR images with overlapped obstacles is less than the predetermined threshold, in operation 704, it is determined whether the number of iteration exceeds a predetermined threshold. If not, at least one of the parameters is adjusted in operation 705 and the above operations are iteratively performed. Otherwise, in operation 706, the set of parameters that produce the highest number of LIDAR images with overlapped obstacle is selected as the optimal parameters.

Note that some or all of the components as shown and described above may be implemented in software, hardware, or a combination thereof. For example, such components can be implemented as software installed and stored in a persistent storage device, which can be loaded and executed in a memory by a processor (not shown) to carry out the processes or operations described throughout this application. Alternatively, such components can be implemented as executable code programmed or embedded into dedicated hardware such as an integrated circuit (e.g., an application specific IC or ASIC), a digital signal processor (DSP), or a field programmable gate array (FPGA), which can be accessed via a corresponding driver and/or operating system from an application. Furthermore, such components can be implemented as specific hardware logic in a processor or processor core as part of an instruction set accessible by a software component via one or more specific instructions.

FIG. 8 is a block diagram illustrating an example of a data processing system which may be used with one embodiment of the disclosure. For example, system 1500 may represent any of data processing systems described above performing any of the processes or methods described above, such as, for example, perception and planning system 110 or any of servers 103-104 of FIG. 1. System 1500 can include many different components. These components can be implemented as integrated circuits (ICs), portions thereof, discrete electronic devices, or other modules adapted to a circuit board such as a motherboard or add-in card of the computer system, or as components otherwise incorporated within a chassis of the computer system.

Note also that system 1500 is intended to show a high level view of many components of the computer system. However, it is to be understood that additional components may be present in certain implementations and furthermore, different arrangement of the components shown may occur in other implementations. System 1500 may represent a desktop, a laptop, a tablet, a server, a mobile phone, a media player, a personal digital assistant (PDA), a Smartwatch, a personal communicator, a gaming device, a network router or hub, a wireless access point (AP) or repeater, a set-top box, or a combination thereof. Further, while only a single machine or system is illustrated, the term “machine” or “system” shall also be taken to include any collection of machines or systems that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.

In one embodiment, system 1500 includes processor 1501, memory 1503, and devices 1505-1508 connected via a bus or an interconnect 1510. Processor 1501 may represent a single processor or multiple processors with a single processor core or multiple processor cores included therein. Processor 1501 may represent one or more general-purpose processors such as a microprocessor, a central processing unit (CPU), or the like. More particularly, processor 1501 may be a complex instruction set computing (CISC) microprocessor, reduced instruction set computing (RISC) microprocessor, very long instruction word (VLIW) microprocessor, or processor implementing other instruction sets, or processors implementing a combination of instruction sets. Processor 1501 may also be one or more special-purpose processors such as an application specific integrated circuit (ASIC), a cellular or baseband processor, a field programmable gate array (FPGA), a digital signal processor (DSP), a network processor, a graphics processor, a communications processor, a cryptographic processor, a co-processor, an embedded processor, or any other type of logic capable of processing instructions.

Processor 1501, which may be a low power multi-core processor socket such as an ultra-low voltage processor, may act as a main processing unit and central hub for communication with the various components of the system. Such processor can be implemented as a system on chip (SoC). Processor 1501 is configured to execute instructions for performing the operations and steps discussed herein. System 1500 may further include a graphics interface that communicates with optional graphics subsystem 1504, which may include a display controller, a graphics processor, and/or a display device.

Processor 1501 may communicate with memory 1503, which in one embodiment can be implemented via multiple memory devices to provide for a given amount of system memory. Memory 1503 may include one or more volatile storage (or memory) devices such as random access memory (RAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), static RAM (SRAM), or other types of storage devices. Memory 1503 may store information including sequences of instructions that are executed by processor 1501, or any other device. For example, executable code and/or data of a variety of operating systems, device drivers, firmware (e.g., input output basic system or BIOS), and/or applications can be loaded in memory 1503 and executed by processor 1501. An operating system can be any kind of operating systems, such as, for example, Robot Operating System (ROS), Windows® operating system from Microsoft®, Mac OS®/iOS® from Apple, Android® from Google®, LINUX, UNIX, or other real-time or embedded operating systems.

System 1500 may further include IO devices such as devices 1505-1508, including network interface device(s) 1505, optional input device(s) 1506, and other optional IO device(s) 1507. Network interface device 1505 may include a wireless transceiver and/or a network interface card (NIC). The wireless transceiver may be a WiFi transceiver, an infrared transceiver, a Bluetooth transceiver, a WiMax transceiver, a wireless cellular telephony transceiver, a satellite transceiver (e.g., a global positioning system (GPS) transceiver), or other radio frequency (RF) transceivers, or a combination thereof. The NIC may be an Ethernet card.

Input device(s) 1506 may include a mouse, a touch pad, a touch sensitive screen (which may be integrated with display device 1504), a pointer device such as a stylus, and/or a keyboard (e.g., physical keyboard or a virtual keyboard displayed as part of a touch sensitive screen). For example, input device 1506 may include a touch screen controller coupled to a touch screen. The touch screen and touch screen controller can, for example, detect contact and movement or break thereof using any of a plurality of touch sensitivity technologies, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with the touch screen.

IO devices 1507 may include an audio device. An audio device may include a speaker and/or a microphone to facilitate voice-enabled functions, such as voice recognition, voice replication, digital recording, and/or telephony functions. Other IO devices 1507 may further include universal serial bus (USB) port(s), parallel port(s), serial port(s), a printer, a network interface, a bus bridge (e.g., a PCI-PCI bridge), sensor(s) (e.g., a motion sensor such as an accelerometer, gyroscope, a magnetometer, a light sensor, compass, a proximity sensor, etc.), or a combination thereof. Devices 1507 may further include an imaging processing subsystem (e.g., a camera), which may include an optical sensor, such as a charged coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) optical sensor, utilized to facilitate camera functions, such as recording photographs and video clips. Certain sensors may be coupled to interconnect 1510 via a sensor hub (not shown), while other devices such as a keyboard or thermal sensor may be controlled by an embedded controller (not shown), dependent upon the specific configuration or design of system 1500.

To provide for persistent storage of information such as data, applications, one or more operating systems and so forth, a mass storage (not shown) may also couple to processor 1501. In various embodiments, to enable a thinner and lighter system design as well as to improve system responsiveness, this mass storage may be implemented via a solid state device (SSD). However in other embodiments, the mass storage may primarily be implemented using a hard disk drive (HDD) with a smaller amount of SSD storage to act as a SSD cache to enable non-volatile storage of context state and other such information during power down events so that a fast power up can occur on re-initiation of system activities. Also a flash device may be coupled to processor 1501, e.g., via a serial peripheral interface (SPI). This flash device may provide for non-volatile storage of system software, including BIOS as well as other firmware of the system.

Storage device 1508 may include computer-accessible storage medium 1509 (also known as a machine-readable storage medium or a computer-readable medium) on which is stored one or more sets of instructions or software (e.g., module, unit, and/or logic 1528) embodying any one or more of the methodologies or functions described herein. Processing module/unit/logic 1528 may represent any of the components described above, such as, for example, planning module 305, control module 306, or LIDAR calibration module 400. Processing module/unit/logic 1528 may also reside, completely or at least partially, within memory 1503 and/or within processor 1501 during execution thereof by data processing system 1500, memory 1503 and processor 1501 also constituting machine-accessible storage media. Processing module/unit/logic 1528 may further be transmitted or received over a network via network interface device 1505.

Computer-readable storage medium 1509 may also be used to store the some software functionalities described above persistently. While computer-readable storage medium 1509 is shown in an exemplary embodiment to be a single medium, the term “computer-readable storage medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The terms “computer-readable storage medium” shall also be taken to include any medium that is capable of storing or encoding a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the present disclosure. The term “computer-readable storage medium” shall accordingly be taken to include, but not be limited to, solid-state memories, and optical and magnetic media, or any other non-transitory machine-readable medium.

Processing module/unit/logic 1528, components and other features described herein can be implemented as discrete hardware components or integrated in the functionality of hardware components such as ASICS, FPGAs, DSPs or similar devices. In addition, processing module/unit/logic 1528 can be implemented as firmware or functional circuitry within hardware devices. Further, processing module/unit/logic 1528 can be implemented in any combination hardware devices and software components.

Note that while system 1500 is illustrated with various components of a data processing system, it is not intended to represent any particular architecture or manner of interconnecting the components; as such details are not germane to embodiments of the present disclosure. It will also be appreciated that network computers, handheld computers, mobile phones, servers, and/or other data processing systems which have fewer components or perhaps more components may also be used with embodiments of the disclosure.

Some portions of the preceding detailed descriptions have been presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the ways used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, conceived to be a self-consistent sequence of operations leading to a desired result. The operations are those requiring physical manipulations of physical quantities.

It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the above discussion, it is appreciated that throughout the description, discussions utilizing terms such as those set forth in the claims below, refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.

Embodiments of the disclosure also relate to an apparatus for performing the operations herein. Such a computer program is stored in a non-transitory computer readable medium. A machine-readable medium includes any mechanism for storing information in a form readable by a machine (e.g., a computer). For example, a machine-readable (e.g., computer-readable) medium includes a machine (e.g., a computer) readable storage medium (e.g., read only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices).

The processes or methods depicted in the preceding figures may be performed by processing logic that comprises hardware (e.g. circuitry, dedicated logic, etc.), software (e.g., embodied on a non-transitory computer readable medium), or a combination of both. Although the processes or methods are described above in terms of some sequential operations, it should be appreciated that some of the operations described may be performed in a different order. Moreover, some operations may be performed in parallel rather than sequentially.

Embodiments of the present disclosure are not described with reference to any particular programming language. It will be appreciated that a variety of programming languages may be used to implement the teachings of embodiments of the disclosure as described herein.

In the foregoing specification, embodiments of the disclosure have been described with reference to specific exemplary embodiments thereof. It will be evident that various modifications may be made thereto without departing from the broader spirit and scope of the disclosure as set forth in the following claims. The specification and drawings are, accordingly, to be regarded in an illustrative sense rather than a restrictive sense. 

What is claimed is:
 1. A computer-implemented method, comprising: receiving a plurality of LIDAR images captured by a LIDAR device of an autonomous driving vehicle (ADV); for each of the LIDAR images, determining using a perception method a location of an obstacle captured in the LIDAR image in a local coordinate system, and transforming using a coordinate converter the LIDAR image from the local coordinate system to a global coordinate system; and optimizing the coordinate converter based on a location of the obstacle appearing in the transformed LIDAR images by iteratively adjusting one or more parameters of the coordinate converter, wherein the optimized coordinate converter is utilized to process subsequent LIDAR images during autonomous driving at real-time.
 2. The method of claim 1, further comprising examining the transformed LIDAR images to determine a consistency of the obstacle appearing in the transformed LIDAR images.
 3. The method of claim 2, further comprising iteratively performing determining using a perception method, transforming using a coordinate converter, and examining the transformed LIDAR images, until the consistency of the obstacle appearance in the LIDAR images is greater than a predetermined threshold.
 4. The method of claim 2, further comprising iteratively performing determining using a perception method, transforming using a coordinate converter, and examining the transformed LIDAR images, until a number of iterations reaches a predetermined threshold.
 5. The method of claim 4, wherein when the number of iterations reaches the predetermined threshold, a set of parameters of the coordinate converter with a highest consistency is selected as an optimal set of parameters for configuring the coordinate converter for autonomous driving at real-time.
 6. The method of claim 1, further comprising counting a number of the transformed LIDAR images that includes an obstacle whose location overlaps with an obstacle of another LIDAR image.
 7. The method of claim 6, wherein the optimized coordinate converter produces a largest number of LIDAR images having an overlapped obstacle with another LIDAR image.
 8. The method of claim 1, wherein the coordinate converter comprises a quaternion function.
 9. The method of claim 1, wherein optimizing the coordinate converter is performed using a gradient decent method.
 10. A non-transitory machine-readable medium having instructions stored therein, which when executed by a processor, cause the processor to perform operations, the operations comprising: receiving a plurality of LIDAR images captured by a LIDAR device of an autonomous driving vehicle (ADV); for each of the LIDAR images, determining using a perception method a location of an obstacle captured in the LIDAR image in a local coordinate system, and transforming using a coordinate converter the LIDAR image from the local coordinate system to a global coordinate system; and optimizing the coordinate converter based on a location of the obstacle appearing in the transformed LIDAR images by iteratively adjusting one or more parameters of the coordinate converter, wherein the optimized coordinate converter is utilized to process subsequent LIDAR images during autonomous driving at real-time.
 11. The machine-readable medium of claim 10, wherein the operations further comprise examining the transformed LIDAR images to determine a consistency of the obstacle appearing in the transformed LIDAR images.
 12. The machine-readable medium of claim 11, wherein the operations further comprise iteratively performing determining using a perception method, transforming using a coordinate converter, and examining the transformed LIDAR images, until the consistency of the obstacle appearance in the LIDAR images is greater than a predetermined threshold.
 13. The machine-readable medium of claim 11, wherein the operations further comprise iteratively performing determining using a perception method, transforming using a coordinate converter, and examining the transformed LIDAR images, until a number of iterations reaches a predetermined threshold.
 14. The machine-readable medium of claim 13, wherein when the number of iterations reaches the predetermined threshold, a set of parameters of the coordinate converter with a highest consistency is selected as an optimal set of parameters for configuring the coordinate converter for autonomous driving at real-time.
 15. The machine-readable medium of claim 10, wherein the operations further comprise counting a number of the transformed LIDAR images that includes an obstacle whose location overlaps with an obstacle of another LIDAR image.
 16. The machine-readable medium of claim 15, wherein the optimized coordinate converter produces a largest number of LIDAR images having an overlapped obstacle with another LIDAR image.
 17. A data processing system, comprising: a processor; and a memory coupled to the processor to store instructions, which when executed by the processor, cause the processor to perform operations, the operations including receiving a plurality of LIDAR images captured by a LIDAR device of an autonomous driving vehicle (ADV), for each of the LIDAR images, determining using a perception method a location of an obstacle captured in the LIDAR image in a local coordinate system, and transforming using a coordinate converter the LIDAR image from the local coordinate system to a global coordinate system, and optimizing the coordinate converter based on a location of the obstacle appearing in the transformed LIDAR images by iteratively adjusting one or more parameters of the coordinate converter, wherein the optimized coordinate converter is utilized to process subsequent LIDAR images during autonomous driving at real-time.
 18. The system of claim 17, wherein the operations further comprise examining the transformed LIDAR images to determine a consistency of the obstacle appearing in the transformed LIDAR images.
 19. The system of claim 18, wherein the operations further comprise iteratively performing determining using a perception method, transforming using a coordinate converter, and examining the transformed LIDAR images, until the consistency of the obstacle appearance in the LIDAR images is greater than a predetermined threshold.
 20. The system of claim 18, wherein the operations further comprise iteratively performing determining using a perception method, transforming using a coordinate converter, and examining the transformed LIDAR images, until a number of iterations reaches a predetermined threshold.
 21. The system of claim 20, wherein when the number of iterations reaches the predetermined threshold, a set of parameters of the coordinate converter with a highest consistency is selected as an optimal set of parameters for configuring the coordinate converter for autonomous driving at real-time.
 22. The system of claim 17, wherein the operations further comprise counting a number of the transformed LIDAR images that includes an obstacle whose location overlaps with an obstacle of another LIDAR image.
 23. The system of claim 22, wherein the optimized coordinate converter produces a largest number of LIDAR images having an overlapped obstacle with another LIDAR image. 